QOS Control Method and Device

ABSTRACT

A QoS control method and a device are disclosed. In the method, a session management function SMF entity obtains service data flow SDF-level QoS control information; the SMF entity sends the SDF-level QoS control information to a terminal; and the terminal performs QoS control on an uplink data packet based on the SDF-level QoS control information, or deletes the SDF-level QoS control information. In the foregoing method embodiments, the terminal can perform the QoS control on the uplink data packet based on the SDF-level QoS control information.

CROSS-REFERENCE

This application is a continuation of International Application No.PCT/CN2017/083671, filed on May 9, 2017, which is hereby incorporated byreference in its entirety.

TECHNICAL FIELD

This application relates to the field of communications technologies,and in particular, to a QoS (quality of service) control method and adevice.

BACKGROUND

Wireless networks have been used by more people or machines, and moreservices are carried on the wireless networks. Various services such asa call, a conference call, an emergency call, and a public warning inthe wireless networks have respective clear service assurancerequirements.

Due to limited radio resources, if a relatively large quantity ofservices need to be simultaneously processed, access, resourcescheduling, and the like need to be controlled based on a QoS rule and apriority of each service. For example, when a user A is in a call, auser B starts downloading a file. Due to limited radio resources, if thedownload service of the user B preempts a radio resource of the callservice of the user A, user experience is extremely terrible. Therefore,a priority higher than that of the download service needs to be set forthe call service, to preferentially ensure radio resource scheduling ofthe call service when radio resources are insufficient.

Specifically, a QoS architecture may be shown in FIG. 1. A terminal mayestablish one or more PDU (packet data unit) sessions with a 5G corenetwork, and a RAN (radio access network)/AN (access network)establishes one or more data radio bearers (DRB) for each PDU session.One DRB includes one or more QoS flows, and each QoS flow iscorresponding to one or more packet filters (packet filter). Forexample, if a QoS flow 1 is corresponding to a packet filter 1 and apacket filter 2, only a data packet that can pass through the packetfilter 1 or the packet filter 2 can be transmitted by using the QoS flow1. In addition, one QoS flow is corresponding to one group of QoSparameters, and same QoS processing is performed on data packetstransmitted by using a same QoS flow.

Different services are corresponding to different SDFs (service dataflow), and one SDF may be corresponding to one or more packet filters orone application detection filter. For example, if a service 1 iscorresponding to an SDF 1, and the SDF 1 is corresponding to a packetfilter 3 and a packet filter 4, a data packet belonging to the service 1can pass through the packet filter 3 or the packet filter 4.

Mapping rules are different when QoS control is performed on anuplink/downlink data packet on a terminal side and a network side, to bespecific, when the uplink/downlink data packet is mapped to a QoS flow.Therefore, in some particular cases, the uplink/downlink data packet maybe mapped to different QoS flows on the terminal side and the networkside, causing a packet loss.

SUMMARY

Embodiments of this application provide a QoS control method and adevice, to perform QoS control on an uplink data packet.

According to a first aspect, an embodiment of this application providesa QoS control method, including: obtaining, by a session managementfunction SMF entity, service data flow SDF-level QoS controlinformation; and sending, by the SMF entity, the SDF-level QoS controlinformation to a terminal.

In a possible implementation, the method further includes: sending, bythe SMF entity, the SDF-level QoS control information to a user planefunction UPF entity, so that the UPF verifies QoS control on an uplinkdata packet based on the SDF-level QoS control information, or deletesthe SDF-level QoS control information.

In a possible implementation, the obtaining, by an SMF entity, SDF-levelQoS control information includes: obtaining, by the SMF entity, theSDF-level QoS control information based on a session management requestsent by a policy control function PCF entity; or obtaining, by the SMFentity, the SDF-level QoS control information based on a local policy.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and at least one ofor any combination of the following: at least one packet filtercorresponding to the SDF, a priority, a QoS flow identifier, and a QoSparameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, the method further includes: sending, bythe SMF entity to an access network device, the QoS flow identifier, orthe QoS flow identifier and the QoS parameter corresponding to the QoSflow, so that the access network device establishes, releases, or bindsto a corresponding air interface resource.

According to a second aspect, an embodiment of this application providesa QoS control method, including: receiving, by a terminal, service dataflow SDF-level QoS control information sent by a session managementfunction SMF entity; and performing, by the terminal, QoS control on anuplink data packet based on the SDF-level QoS control information, ordeleting the SDF-level QoS control information.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and at least one ofor any combination of the following: at least one packet filtercorresponding to the SDF, a priority, a QoS flow identifier, and a QoSparameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, the performing, by the terminal, QoScontrol on an uplink data packet based on the SDF-level QoS controlinformation includes: determining, by the terminal, a matching order ofSDF-level packet filters based on the priority in the SDF-level QoScontrol information; and performing, by the terminal, data packetmatching based on the matching order of the SDF-level packet filters,and performing the QoS control based on a QoS flow corresponding to apacket filter that successfully matches the uplink data packet.

According to a third aspect, an embodiment of the present applicationprovides a session management function SMF entity. The sessionmanagement function SMF entity has a function of implementing thesession management function SMF entity in the foregoing method examples.The function may be implemented by hardware, or may be implemented byhardware by executing corresponding software. The hardware or softwareincludes one or more modules corresponding to the function.

In a possible design, a structure of the session management function SMFentity includes a processing unit and a communications unit. Theprocessing unit is configured to support the session management functionSMF entity in performing a corresponding function in the foregoingmethods. The communications unit is configured to support communicationbetween the session management function SMF entity and another device.The session management function SMF entity may further include a storageunit, and the storage unit is configured to be coupled to the processingunit, and stores a program instruction and data that are necessary forthe session management function SMF entity.

For example, the processing unit may be a processor, the communicationsunit may be a transceiver, and the storage unit may be a memory.

According to a fourth aspect, an embodiment of this application providesa session management function SMF entity, including: a processor, and amemory and a transceiver that are separately connected to the processor,where the processor is configured to invoke a computer programpre-stored in the memory to perform the following steps: obtainingservice data flow SDF-level QoS control information; and sending theSDF-level QoS control information to a terminal by using thetransceiver.

In a possible implementation, the processor is further configured tosend the SDF-level QoS control information to a user plane function UPFentity by using the transceiver, so that the UPF verifies QoS control onan uplink data packet based on the SDF-level QoS control information, ordeletes the SDF-level QoS control information.

In a possible implementation, when obtaining the SDF-level QoS controlinformation, the processor is specifically configured to: obtain theSDF-level QoS control information based on a session management requestsent by a policy control function PCF entity; or obtain the SDF-levelQoS control information based on a local policy.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and at least one ofor any combination of the following: at least one packet filtercorresponding to the SDF, a priority, a QoS flow identifier, and a QoSparameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, the processor is further configured to:send, to an access network device by using the transceiver, the QoS flowidentifier, or the QoS flow identifier and the QoS parametercorresponding to the QoS flow, so that the access network deviceestablishes, releases, or binds to a corresponding air interfaceresource.

According to a fifth aspect, an embodiment of the present applicationprovides a terminal. The terminal has a function of implementing theterminal behaviors in the foregoing method examples. The function may beimplemented by hardware, or may be implemented by hardware by executingcorresponding software. The hardware or software includes one or moremodules corresponding to the function.

In a possible design, a structure of the terminal includes a processingunit and a communications unit. The processing unit is configured tosupport the terminal in performing a corresponding function in theforegoing methods. The communications unit is configured to supportcommunication between the terminal and another device. The terminal mayfurther include a storage unit, and the storage unit is configured to becoupled to the processing unit, and stores a program instruction anddata that are necessary for the terminal.

For example, the processing unit may be a processor, the communicationsunit may be a transceiver, and the storage unit may be a memory.

According to a sixth aspect, an embodiment of this application providesa terminal, including: a processor, and a memory and a transceiver thatare separately connected to the processor, where the processor isconfigured to invoke a computer program pre-stored in the memory toperform the following steps: receiving, by using the transceiver,service data flow SDF-level QoS control information sent by a sessionmanagement function SMF entity; and performing QoS control on an uplinkdata packet based on the SDF-level QoS control information, or deletingthe SDF-level QoS control information.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and at least one ofor any combination of the following: at least one packet filtercorresponding to the SDF, a priority, a QoS flow identifier, and a QoSparameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, the processor is further configured to:determine a matching order of SDF-level packet filters based on thepriority in the SDF-level QoS control information; and perform datapacket matching based on the matching order of the SDF-level packetfilters, and perform the QoS control based on a QoS flow correspondingto a packet filter that successfully matches the uplink data packet.

According to a seventh aspect, an embodiment of the present applicationprovides a communications system. The system includes the sessionmanagement function SMF entity according to the foregoing aspects. Inanother possible design, the system may further include another devicesuch as a PCF, a UPF, or a terminal device that interacts with thesession management function SMF entity in the solutions provided in theembodiments of the present application.

According to an eighth aspect, an embodiment of the present applicationprovides a computer storage medium, configured to store a computersoftware instruction used by the foregoing session management functionSMF entity, and the instruction includes a program designed to performthe foregoing aspects.

According to a ninth aspect, an embodiment of the present applicationprovides a computer storage medium, configured to store a computersoftware instruction used by the foregoing terminal, and the instructionincludes a program designed to perform the foregoing aspects.

According to a tenth aspect, this application further provides acomputer program product including an instruction. When run on acomputer, the computer program product causes the computer to performthe methods according to the foregoing aspects.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a QoS architecture according to anembodiment of this application;

FIG. 2 is a schematic diagram of mapping an uplink/downlink data packetto a QoS flow according to an embodiment of this application;

FIG. 3 is a schematic diagram of a matching error occurring when anuplink/downlink data packet is mapped to a QoS flow according to anembodiment of this application;

FIG. 4 is a schematic diagram of a system architecture applicable to theembodiments of this application according to an embodiment of thisapplication;

FIG. 5 is a schematic flowchart of a QoS control method according to anembodiment of this application;

FIG. 6 is a schematic flowchart of specific Embodiment 1 according toembodiments of this application;

FIG. 7 is a schematic flowchart of specific Embodiment 2 according toembodiments of this application;

FIG. 8 is a schematic flowchart of specific Embodiment 3 according toembodiments of this application;

FIG. 9 is a first schematic structural diagram of an SMF entityaccording to an embodiment of this application;

FIG. 10 is a second schematic structural diagram of an SMF entityaccording to an embodiment of this application;

FIG. 11 is a first schematic structural diagram of a terminal accordingto an embodiment of this application; and

FIG. 12 is a second schematic structural diagram of a terminal accordingto an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

The following further describes the embodiments of this application indetail with reference to the accompanying drawings.

The applicant finds during research that, the following problem existswhen a terminal and a device on a network side perform QoS control on anuplink/downlink data packet in the prior art:

A NAS (non-access stratum) of the terminal and a UPF (user planefunction) on the network side map the uplink/downlink data packet to aQoS flow based on a packet filter (packet filter); and an AS (accessstratum) of the terminal and a RAN/AN associate an uplink/downlink QoSflow with a DRB. When the terminal and the UPF on the network side mapthe data packet to the QoS flow, a specific mapping mechanism may beshown in FIG. 2. Details are as follows:

On a terminal side, for the terminal, each QoS flow is corresponding toone QoS flow template, each QoS flow template is corresponding to one ormore packet filters, and each QoS flow template has one priority. Whensending a data packet, the terminal sequentially performs matchingbetween the data packet and QoS flow templates in descending order ofpriorities of the QoS flow templates, and stops matching when acorresponding QoS flow template is found through matching. Specifically,matching is first performed between the data packet and a QoS flowtemplate with a highest priority. If the data packet can pass throughany packet filter corresponding to the QoS flow template, the matchingsucceeds, and the data packet is transmitted by using a QoS flowcorresponding to the QoS flow template; otherwise, matching continues tobe performed between the data packet and a QoS flow template with alower priority, until a corresponding QoS flow template is found throughmatching.

On the network side, for the UPF, each SDF is corresponding to one ormore packet filters, and each SDF is corresponding to one priority. Whensending a data packet, a network device sequentially performs matchingbetween the data packet and packet filters of SDFs based on prioritiesof the SDFs, and stops matching when a packet filter of a correspondingSDF is found through matching. Specifically, matching is first performedbetween the data packet and a packet filter of an SDF with a highestpriority. If the data packet can pass through the packet filter of theSDF, the matching succeeds, and the data packet is transmitted by usinga QoS flow corresponding to the packet filter of the SDF; otherwise,matching continues to be performed between the data packet and a packetfilter of an SDF with a lower priority.

In the foregoing mechanism, different matching rules are used on theterminal side and the network side to perform data packet matching.Consequently, different QoS flows may be found through matching for asame data packet on the terminal side and the network side, causing apacket loss. Specifically, as shown in FIG. 3, when a terminal needs totransmit a data packet, if the data packet can match both a packetfilter of an SDF a and a packet filter of an SDF b, due to differentmatching priorities, the uplink data packet may match a QoS flow 1 on aterminal side, and the data packet may match a QoS flow 2 on a networkside. During uplink data transmission, it may be verified, on thenetwork side, whether a correct QoS flow is used for the data packetsent by the terminal. If it is determined, on the network side, that theterminal uses an incorrect QoS flow, the data packet is discarded on thenetwork side.

To resolve the foregoing technical problem, the embodiments of thisapplication provide a QoS control method and a device.

The terminal in this application may include a handheld device, anin-vehicle device, a wearable device, or a computing device that has awireless communication function, or another processing device connectedto a wireless modem, and various forms of UEs (user equipment), MSs(mobile station), terminal devices, and the like.

The QoS control method provided in the embodiments of this applicationmay be applied to a 5G network architecture shown in FIG. 4.

Main functions of a UPF (user plane function) include: data packetrouting and transmission, packet detection, service usage reporting, QoSprocessing, lawful interception, uplink packet detection, downlink datapacket storage, and other user plane related functions.

Main functions of an AMF (access and mobility management function)include: connection management, mobility management, registrationmanagement, access authentication and authorization, accessibilitymanagement, security context management, and other access and mobilityrelated functions.

Main functions of an SMF (session management function) include: sessionmanagement (for example, session establishment, modification, andrelease, including tunnel maintenance between a UPF and an RAN/AN), UPFselection and control, SSC (service and session continuity) modeselection, roaming, and other session related functions.

Main functions of a PCF (policy control function) include: unifiedpolicy development, policy control provisioning, obtaining policy anddecision related subscription information from a UDR, and other policyrelated functions.

A main function of an AUSF (authentication server function) includes:authenticating whether user equipment is authorized.

A main function of an AF (application function) is service provisioning,and specifically includes: service routing, access network capabilityenablement, and interaction with a policy architecture.

Main functions of UDM (unified data management) are credential,location, and subscription management, and user subscription datastorage.

A main function of a DN (data network) is providing a specific dataservice, such as an operator service, an Internet access service, or athird-party service.

Certainly, FIG. 4 shows merely an example of an application scenario ofthe embodiments of this application, and constitutes no limitation tothe application scenario of the embodiments of this application. Asystem architecture applicable to the embodiments of this applicationmay include more or fewer network elements than those shown in FIG. 4,or may be a different system architecture such as an EPS systemarchitecture or a CUPS architecture.

Referring to FIG. 5, FIG. 5 is a schematic flowchart of a QoS controlmethod according to an embodiment of this application. As shown in thefigure, the method includes the following steps:

Step 501: An SMF entity obtains SDF-level QoS control information.

Step 502: The SMF entity sends the SDF-level QoS control information toa terminal.

Step 503: The terminal performs QoS control on an uplink data packetbased on the received SDF-level QoS control information, or deletes theSDF-level QoS control information.

In this embodiment, the SDF-level QoS control information obtained bythe SMF entity is used to perform QoS control on an SDF. The SMF entitysends the SDF-level QoS control information to the terminal, so that theterminal performs the QoS control on the uplink data packet.

In a possible implementation, the SDF-level QoS control informationindicates that at least one packet filter corresponding to one SDF iscorresponding to a same QoS flow, to be specific, is corresponding to asame QoS parameter, and each packet filter has a same SDF-levelpriority. However, different SDFs are corresponding to differentpriorities. Different SDFs may be corresponding to a same QoS parameter,to be specific, may be corresponding to a same QoS flow, but prioritiesof packet filters corresponding to the different SDFs are different.

It may be understood that the SDF-level QoS control information includesany one of or any combination of following: an SDF-level identifier, atleast one SDF-level packet filter, an SDF-level priority (namely, apriority of the SDF-level packet filter), a QoS flow identifier, and aQoS parameter. The SDF-level identifier may have a plurality ofrepresentation forms, for example, an SDF identifier (SDF ID), a QoSrule identifier (QoS rule ID), or other various forms of identifiersthat can embody an SDF level.

Similarly, in this embodiment of this application, the SDF-level QoScontrol information obtained by the SMF entity has various specificrepresentation forms, including but not limited to the following threemanners.

In this embodiment of this application, the QoS control informationobtained by the SMF entity is of an SDF level, but has variousrepresentation forms.

In a first manner, an SDF is used as a control unit.

In this manner, the SDF-level QoS control information may include anyone of or any combination of following: an SDF identifier, at least onepacket filter corresponding to the SDF, a priority, a QoS flowidentifier, and a QoS parameter.

Specifically, the following three scenarios may be included.

In a first scenario, a new SDF is added.

In this case, the SDF-level QoS control information obtained by the SMFentity includes: an identifier of the newly added SDF; a packet filter:at least one packet filter corresponding to the SDF; a priority: apriority corresponding to the SDF, namely, a priority of the packetfilter; and a QoS flow identifier: an identifier of a QoS flowcorresponding to the SDF, to be specific, a data packet belonging to theSDF is transmitted by using the QoS flow.

Optionally, the SDF-level QoS control information includes a QoSparameter: a QoS parameter corresponding to the QoS flow, for example, apacket delay, a bit rate, or a packet loss rate.

Further, if the QoS flow is a non-GBR QoS flow (non-guaranteed bit rateQoS flow), the QoS parameter may further include a 5QI (5G QoSIndicator, 5G QoS indicator). If the QoS flow is a GBR QoS flow(guaranteed bit rate QoS flow), the QoS parameter may include a 5QI, anotification (notification), a GFBR (Guaranteed Flow Bit Rate,guaranteed flow bit rate), and an MFBR (Maximum Flow Bit Rate, maximumflow bit rate).

In a second scenario, an existing SDF is modified.

In this case, the SDF-level QoS control information obtained by the SMFentity includes at least an identifier of the to-be-modified SDF, andfurther includes any one of or any combination of the followinginformation: a packet filter: at least one packet filter correspondingto the SDF, or at least one to-be-deleted packet filter corresponding tothe SDF, or at least one updated packet filter corresponding to the SDF;a priority: a modified priority corresponding to the SDF; a QoS flowidentifier: an identifier of a modified QoS flow corresponding to theSDF; and a QoS parameter: a modified QoS parameter corresponding to theSDF.

Further, if the modified QoS flow is a non-GBR QoS flow, the QoSparameter may further include a 5QI. If the QoS flow is a GBR QoS flow,the QoS parameter may include a 5QI, a notification, a GFBR, and anMFBR.

In a third scenario, an existing SDF is deleted.

In this case, the SDF-level QoS control information obtained by the SMFentity may include only an identifier of the to-be-deleted SDF.

In a second manner, an SDF in a QoS flow is used as a control unit.

In this manner, the SDF-level QoS control information may include anyone of or any combination of following: a QoS flow identifier, at leastone SDF identifier, at least one packet filter corresponding to the atleast one SDF, a priority corresponding to the at least one SDF, and aQoS parameter corresponding to the QoS flow.

Specifically, when the QoS flow is used as a QoS control unit, thefollowing three scenarios may be included.

In a first scenario, a new QoS flow is established.

In this case, the SDF-level QoS control information obtained by the SMFentity includes an identifier of the newly established QoS flow, and mayfurther include: an SDF identifier: at least one SDF identifiercorresponding to the newly established QoS flow, for example, an SDFidentifier 1 corresponding to the added QoS flow, and an SDF identifier2 corresponding to the added QoS flow; a packet filter: at least onepacket filter corresponding to each SDF, for example, a packet filter 1and a packet filter 2 that are corresponding to the SDF 1, and a packetfilter 3 and a packet filter 4 that are corresponding to the SDF 2; anda priority: a priority corresponding to each SDF.

Optionally, the SDF-level QoS control information includes a QoSparameter: a QoS parameter corresponding to the newly established QoSflow.

Further, if the newly established QoS flow is a non-GBR QoS flow, theQoS parameter may further include a 5QI. If the newly established QoSflow is a GBR QoS flow, the QoS parameter may include a 5QI, anotification, a GFBR, and an MFBR.

In a second scenario, an existing QoS flow is modified.

In this case, the QoS control information obtained by the SMF entityincludes at least an identifier of the to-be-modified QoS flow, andfurther includes any one of or any combination of the followinginformation: an SDF identifier: an identifier of a to-be-added SDFcorresponding to the QoS flow, or an identifier of a to-be-modified SDFcorresponding to the QoS flow, or an identifier of a to-be-deleted SDFcorresponding to the QoS flow; a packet filter, where if an SDFcorresponding to the QoS flow is to be added, the packet filter includesat least one packet filter corresponding to the added SDF; or if anexisting packet filter corresponding to an SDF 1 corresponding to theQoS flow is modified, the packet filter includes at least oneto-be-added packet filter corresponding to the SDF 1, or at least oneto-be-deleted packet filter corresponding to the SDF 1, or at least onemodified packet filter corresponding to a to-be-modified SDF; apriority, where if an SDF corresponding to the QoS flow is to be added,the priority includes a priority corresponding to the to-be-added SDF;or if a priority of an SDF corresponding to the QoS flow is modified,the priority includes a modified priority corresponding to the SDF; anda QoS parameter: a modified QoS parameter corresponding to the QoS flow.

Further, if the modified QoS flow is a non-GBR QoS flow, the QoSparameter may further include a 5QI. If the modified QoS flow is a GBRQoS flow, the QoS parameter may include a 5QI, a notification, a GFBR,and an MFBR.

In a third scenario, an existing QoS flow is deleted.

In this case, the SDF-level QoS control information obtained by the SMFentity may include an identifier of the to-be-deleted QoS flow.

In a third manner, a QoS rule is used as a control unit.

In this manner, one QoS rule is corresponding to one SDF. The SDF-levelQoS control information may include any one of or any combination of thefollowing: a QoS rule identifier, at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

Specifically, when the QoS flow is used as a QoS control unit, thefollowing three scenarios may be included.

In a first scenario, a QoS rule is added.

In this case, the SDF-level QoS control information obtained by the SMFentity includes an identifier of the newly added QoS rule, and furtherincludes the following information: a packet filter: at least one packetfilter corresponding to the added QoS rule; a priority: a prioritycorresponding to the added QoS rule, namely, a priority of the packetfilter; and a QoS flow identifier: a QoS flow identifier correspondingto the added QoS rule.

Optionally, the SDF-level QoS control information includes a QoSparameter: a QoS parameter corresponding to the QoS flow.

Further, if the QoS flow corresponding to the added QoS rule is anon-GBR QoS flow, the QoS parameter may further include a 5QI. If theQoS flow corresponding to the added QoS rule is a GBR QoS flow, the QoSparameter may include a 5QI, a notification, a GFBR, and an MFBR.

In a second scenario, an existing QoS rule is modified.

In this case, the SDF-level QoS control information obtained by the SMFentity includes at least an identifier of the to-be-modified QoS rule,and further includes any one of or any combination of the followinginformation: a packet filter: at least one to-be-added packet filtercorresponding to the QoS rule, or at least one to-be-deleted packetfilter corresponding to the QoS rule, or at least one modified packetfilter corresponding to the QoS rule; a priority: a modified prioritycorresponding to the QoS rule; a QoS flow identifier: an identifier of amodified QoS flow corresponding to the QoS rule; and a QoS parameter: amodified QoS parameter corresponding to the modified QoS flow.

Further, if the modified QoS flow is a non-GBR QoS flow, the QoSparameter may further include a 5QI. If the modified QoS flow is a GBRQoS flow, the QoS parameter may include a 5QI, a notification, a GFBR,and an MFBR.

In a third scenario, an existing QoS rule is deleted.

In this case, the SDF-level QoS control information obtained by the SMFentity may include only an identifier of the to-be-deleted QoS rule.

During specific implementation, one of the foregoing three manners maybe selected based on a specific application requirement. The SDF-levelQoS control information is sent to the terminal, so that the terminalperforms the QoS control on the uplink data packet based on theSDF-level QoS control information.

In a possible implementation, the SMF entity may further send theSDF-level QoS control information to a UPF entity, so that the UPFentity verifies the QoS control on the uplink data packet based on theSDF-level QoS control information.

The SMF entity sends the SDF-level QoS control information to theterminal and the UPF entity, so that the terminal and the UPF canseparately perform the QoS control on the uplink data packet based onthe same QoS control information, thereby avoiding a packet loss causedby different QoS control performed by the terminal and the UPF on uplinkdata.

In some embodiments, the SMF entity may further send, to an accessnetwork device, the following two types of information: the QoS flowidentifier, or the QoS flow identifier and the QoS parametercorresponding to the QoS flow, so that the access network deviceestablishes, deletes, or binds to a corresponding air interface resourcebased on the foregoing information.

In a possible implementation, step 501 performed by the SMF entity isspecifically: receiving a policy control rule or a QoS control rule sentby a PCF entity, and obtaining, by the SMF, the SDF-level QoS controlinformation based on the received policy control rule or QoS controlrule. Specifically, the PCF entity may send a PDU-CAN sessionmodification instruction to the SMF entity, where the policy controlrule or the QoS control rule is carried in the PDU session modificationinstruction.

In another possible implementation, step 501 performed by the SMF entityis specifically: obtaining the SDF-level QoS control information basedon a policy stored in the SMF entity.

In either of the foregoing possible implementations, a policy stored inthe PCF entity or the policy stored in the SMF entity includes a basisof updating the SDF-level QoS control information. For example, whennetwork load meets a preset condition, the PCF entity or the SMF entityneeds to update the SDF-level QoS control information, to ensure thatQoS of an important service is not affected.

Further, in step 503, that the terminal performs QoS control on anuplink data packet specifically includes: determining, by the terminal,a matching order of SDF-level packet filters based on the priority inthe received SDF-level QoS control information; and performing datapacket matching based on the matching order of the SDF-level packetfilters, and performing the QoS control based on a QoS flowcorresponding to a packet filter that successfully matches the uplinkdata packet.

For clearer understanding of the QoS control method provided in theembodiments of the present application, several specific embodiments areused for description below.

Embodiment 1

A specific procedure is described with reference to FIG. 6.

Step 601: A PCF entity sends a PDU-CAN (PDU-connectivity access network)session modification request to an SMF entity, where the requestincludes a policy control rule information.

Further, the request may further include a QoS requirement.

Optionally, the policy control rule information is used to establish anew policy control rule; or the policy control rule information is usedto modify an existing policy control rule; or the policy control ruleinformation is used to delete an existing policy control rule.

Step 602: After receiving the PDU-CAN session modification request, theSMF entity determines to perform a PDU session update procedure.

Step 603: The SMF entity sends a session management request to an AMFentity, where the session management request includes NAS signaling (forexample, a PDU session modification command, where the PDU sessionmodification command is used as an example for description in thefigure), and the NAS signaling includes the foregoing SDF-level QoScontrol information, namely, SDF information.

If the SMF entity determines, based on the received policy control ruleinformation, to establish a new SDF, the SDF-level QoS controlinformation includes: an SDF identifier (SDF ID) of the newlyestablished SDF, at least one packet filter corresponding to the SDF, apriority, and a QoS parameter. For example, a format of the SDF-levelQoS control information may be: SDF ID, QoS parameters, QFI, Precedencevalue, Filters.

Further, if an established QoS flow can meet a QoS requirement of thenewly established SDF, the SDF-level QoS control information includes aQoS flow identifier (QoS flow ID, QFI for short) of the established QoSflow. If no established QoS flow can meet a QoS requirement of the newlyestablished SDF, the SDF-level QoS control information includes a QFI ofa newly established QoS flow. Further, if the newly established QoS flowis a non-GBR QoS flow, the QoS parameter may include a 5QI. If the newlyestablished QoS flow is a GBR QoS flow, the QoS parameter may include a5QI, a notification, a GFBR, and an MFBR.

If the SMF entity determines, based on the received policy control ruleinformation, to modify a policy control rule of a QoS requirement of anexisting SDF, the SDF-level QoS control information includes an ID ofthe to-be-modified SDF. If an established QoS flow can meet a modifiedQoS requirement, the SDF-level QoS control information includes a QFI ofthe established QoS flow. If no established QoS flow can meet a modifiedQoS requirement, the SDF-level QoS control information includes a QFI ofa newly established QoS flow and a QoS parameter corresponding to thenew QoS flow. For example, a format of the SDF-level QoS controlinformation may be: Update-SDF QoS: SDF ID, QFI, QoS parameters.Further, if the newly established QoS flow is a non-GBR QoS flow, theQoS parameter may include a 5QI. If the newly established QoS flow is aGBR QoS flow, the QoS parameter may include a 5QI, a notification, aGFBR, and an MFBR. The QoS parameter is optional.

If the SMF entity determines, based on the received policy control ruleinformation, to modify a packet filter and/or a priority correspondingto an existing SDF, the SDF-level QoS control information includes an IDof the to-be-modified SDF, and a modified priority and/or a modifiedpacket filter. For example, a format of the SDF-level QoS controlinformation may be: Update-SDF Filters/Precedence: SDF ID,Filters/Precedence value.

If the SMF entity determines, based on the received policy control ruleinformation, to delete an existing SDF, the SDF-level QoS controlinformation includes an ID of the to-be-deleted SDF. For example, aformat of the SDF-level QoS control information may be: Delete-SDF: SDFID, delete operation.

In addition, if the SMF entity determines, based on the received policycontrol rule information, that a new QoS flow needs to be established,the session management request further independently includes QoS flowinformation, where the QoS flow information includes a QFI and a QoSparameter and is used to instruct a RAN/AN to store the QoS flowinformation and establish a corresponding air interface resource or bindthe QoS flow to an existing air interface resource. If the SMF entitydetermines, based on the received policy control rule information, thata QoS flow needs to be deleted, the session management request furtherindependently includes a QFI of the QoS flow, where the QFI is used toinstruct the RAN/AN to release an air interface resource.

Step 604: The AMF sends an N2 session request to a RAN/AN by using an N2interface, where the N2 session request includes NAS signaling (forexample, a PDU session modification command, where the PDU sessionmodification command is used as an example for description in thefigure), and the NAS signaling includes the SDF-level QoS controlinformation.

Optionally, if a new QoS flow needs to be established, the N2 sessionrequest further indicates that the RAN/AN needs to store informationabout the newly established QoS flow, and establish a corresponding airinterface resource with a terminal or bind the newly established QoSflow to an existing air interface resource. If a QoS flow needs to bedeleted, the N2 session request further indicates that the RAN/AN needsto delete corresponding QoS flow information, so that the RAN/ANreleases an air interface resource with the terminal.

Step 605: The RAN/AN sends a radio resource control request to aterminal, where the request includes a PDU session modification command,and the PDU session modification command includes the SDF-level QoScontrol information, so that the terminal performs QoS control on anuplink data packet based on the SDF-level QoS control information, ordeletes the corresponding SDF information.

Step 606: The terminal returns an acknowledgement message to the RAN/ANafter receiving the SDF-level QoS control information.

The terminal stores the SDF-level QoS control information, and performsthe QoS control on the uplink data packet based on the SDF-level QoScontrol information, or deletes the locally stored SDF-level QoS controlinformation.

The SDF-level QoS control information may be stored in the terminal inthe following forms:

-   -   SDF ID1: Precedence value, QFI, Filters;    -   SDF ID2: Precedence value, QFI, Filters;

Step 607: The RAN/AN returns an N2 session response to the AMF by usingthe N2 interface.

Step 608: The AMF returns a session management response to the SMF,where the response includes a PDU session modification acknowledgementmessage.

Step 609: The SMF sends an N4 session modification request to the UPF byusing an N4 interface, where the request optionally includes theSDF-level QoS control information.

When the session modification request is used to add an SDF, the UPFgenerates, based on the SDF-level QoS control information, at least oneSDF-level packet filter in a QoS flow corresponding to the added SDF,and the at least one generated SDF-level packet filter has a samepriority.

When the session modification request is used to modify informationabout an existing SDF, the UPF modifies the information about the SDF.For example, to modify a priority of the existing SDF, the UPF modifiesa priority of a packet filter corresponding to the SDF.

When the session modification request is used to delete an existing SDF,the UPF deletes a packet filter corresponding to the SDF and otherinformation about the SDF.

Step 610: The UPF returns an N4 session modification response to the SMFby using the N4 interface.

Step 611: The SMF returns a PDU-CAN session modification acknowledgementmessage to the PCF.

According to step 601 to step 611, the QoS control information stored inthe terminal and the UPF is modified, so that the terminal and the UPFcan perform QoS control on an uplink/downlink data packet based on thesame SDF-level QoS control information. Certainly, in some cases, forexample, when network load is relatively large, priorities of servicesneed to be rearranged to ensure that QoS of some services is notaffected. Alternatively, the SMF may actively initiate a process ofmodifying the SDF-level QoS control information, to be specific, step601 and step 611 may not be performed.

When needing to send an uplink data packet, the terminal performs, basedon SDF-level priorities, matching between the uplink data packet and apacket filter corresponding to an SDF with a highest priority. If thematching between the uplink data packet and the packet filtercorresponding to the SDF with the highest priority succeeds, theterminal transmits the uplink data packet by using a QoS flowcorresponding to the filter; otherwise, continues to perform matchingbetween the uplink data packet and a packet filter corresponding to anSDF with a second highest priority, until an appropriate packet filteris found through matching. When receiving the uplink data packet, theUPF performs data packet matching based on the same SDF-level QoScontrol information. Therefore, a QoS flow that is corresponding to thedata packet and that is determined by the UPF is the same as a QoS flowdetermined by the terminal, so that a packet loss can be avoided.

Embodiment 2

A specific procedure is described with reference to FIG. 7.

Step 701: A PCF entity sends a PDU-CAN session modification request toan SMF entity, where the request includes a policy control ruleinformation.

Optionally, the policy control rule information is used to establish anew policy control rule; or the policy control rule information is usedto modify an existing policy control rule; or the policy control ruleinformation is used to delete an existing policy control rule.

Step 702: After receiving the PDU-CAN session modification request, theSMF determines to perform a PDU session update procedure.

Step 703: The SMF sends a session management request to an AMF, wherethe session management request includes NAS signaling (for example, aPDU session modification command, where the PDU session modificationcommand is used as an example for description in the figure), and theNAS signaling includes the foregoing SDF-level QoS control information,namely, QoS flow information.

If the SMF entity determines, based on the received policy control ruleinformation, to establish a new QoS flow, the SDF-level QoS controlinformation includes a QFI of the newly established QoS flow, an ID ofan SDF, a priority of the SDF, and a packet filter. The SDFcorresponding to the newly established QoS flow may be an existing SDFor a newly established SDF. For example, a format of the SDF-level QoScontrol information may be: QFI, QoS parameters, SDF ID, Precedencevalue, Filters. Further, if the newly established QoS flow is a non-GBRQoS flow, the QoS parameter may include a 5QI. If the newly establishedQoS flow is a GBR QoS flow, the QoS parameter may include a 5QI, anotification, a GFBR, and an MFBR. The QoS parameter is optional.

If the SMF entity determines, based on the received policy control ruleinformation, to modify an existing QoS flow, the SDF-level QoS controlinformation includes a QFI of the to-be-modified QoS flow, an ID of anSDF, a priority of the SDF, and a packet filter. For a modified SDFcorresponding to the QoS flow, a new SDF may be added, or an existingSDF may be deleted, or a new SDF may not be added and an existing SDFmay not be deleted, but only a priority and/or a packet filter of theexisting SDF is modified. For example, a format of the SDF-level QoScontrol information may be: QFI, SDF ID, Filters/Precedence value.

If the SMF entity determines, based on the received policy control ruleinformation, to delete an existing QoS flow, the SDF-level QoS controlinformation may include only an identifier of the to-be-deleted QoSflow.

In addition, if the SMF entity determines, based on the received policycontrol rule information, that a new QoS flow needs to be established,the session management request further independently includes QoS flowinformation, where the QoS flow information includes a QFI and a QoSparameter and is used to instruct a RAN/AN to store the QoS flowinformation and establish a corresponding air interface resource or bindthe QoS flow to an existing air interface resource. If the SMF entitydetermines, based on the received policy control rule information, thata QoS flow needs to be deleted, the session management request furtherindependently includes a QFI of the QoS flow, where the QFI is used toinstruct the RAN/AN to release an air interface resource.

Step 704: The AMF sends an N2 session request to a RAN/AN by using an N2interface, where the N2 session request includes NAS signaling (forexample, a PDU session modification command, where the PDU sessionmodification command is used as an example for description in thefigure), and the NAS signaling includes the SDF-level QoS controlinformation.

Further, if a new QoS flow needs to be established, the N2 sessionrequest further instructs that the RAN/AN needs to store informationabout the newly established QoS flow, and establish a corresponding airinterface resource with a terminal or bind the newly established QoSflow to an existing air interface resource. If a QoS flow needs to bedeleted, the N2 session request further instructs that the RAN/AN needsto delete corresponding QoS flow information, so that the RAN/ANreleases an air interface resource with the terminal.

Step 705: The RAN/AN sends a radio resource control request to aterminal, where the request includes a PDU session modification command,and the PDU session modification command includes the SDF-level QoScontrol information, so that the terminal performs QoS control on anuplink data packet based on the SDF-level QoS control information, ordeletes the corresponding QoS flow information.

Step 706: The terminal returns an acknowledgement message to the RAN/ANafter receiving the SDF-level QoS control information.

The terminal stores the SDF-level QoS control information, and performsthe QoS control on the uplink data packet based on the SDF-level QoScontrol information, or deletes the locally stored SDF-level QoS controlinformation.

The SDF-level QoS control information may be stored in the terminal inthe following forms:

-   -   QFI 1: SDF ID 1, Precedence value, Filters;        -   SDF ID 2, Precedence value, Filters;    -   QFI 2: SDF ID 3, Precedence value, Filters;        -   SDF ID 4, Precedence value, Filters;

Step 707: The RAN/AN returns an N2 session response to the AMF by usingthe N2 interface.

Step 708: The AMF returns a session management response to the SMF,where the response includes a PDU session modification acknowledgementmessage.

Step 709: The SMF sends an N4 session modification request to the UPF byusing an N4 interface, where the request optionally includes theSDF-level QoS control information.

When the session modification request is used to add a QoS flow, the UPFgenerates, in the added QoS flow based on the SDF-level QoS controlinformation, at least one SDF-level packet filter of an SDFcorresponding to the QoS flow, and the at least one generated SDF-levelpacket filter has a same priority.

When the session modification request is used to modify informationabout an existing QoS flow, the UPF modifies the information about theQoS flow.

When the session modification request is used to delete an existing QoSflow, the UPF deletes information about the QoS flow.

Step 710: The UPF returns an N4 session modification response to the SMFby using the N4 interface.

Step 711: The SMF returns a PDU-CAN modification acknowledgement messageto the PCF.

According to step 701 to step 711, both the terminal and the UPF performQoS control on an uplink/downlink data packet based on the sameSDF-level QoS control information.

When needing to send an uplink data packet, the terminal performs, basedon SDF-level priorities, matching between the uplink data packet and apacket filter corresponding to an SDF with a highest priority. If thematching between the uplink data packet and the packet filtercorresponding to the SDF with the highest priority succeeds, theterminal transmits the uplink data packet by using a QoS flowcorresponding to the filter; otherwise, continues to perform matchingbetween the uplink data packet and a packet filter corresponding to anSDF with a second highest priority, until an appropriate packet filteris found through matching. When receiving the uplink data packet, theUPF performs data packet matching based on the same SDF-level QoScontrol information. Therefore, a QoS flow that is corresponding to thedata packet and that is determined by the UPF is the same as a QoS flowdetermined by the terminal, so that a packet loss can be avoided.

Similarly, in some cases, alternatively, the SMF may actively initiate aprocess of modifying the SDF-level QoS control information, to bespecific, step 701 and step 711 may not be performed.

The SDF-level QoS control information in Embodiment 2 is slightlydifferent from the SDF-level QoS control information in Embodiment 1 inspecific information content and an information format. However, the QoScontrol information in Embodiment 1 and the QoS control information inEmbodiment 2 are both implemented based on an SDF level, and differentSDFs are corresponding to different priorities. Therefore, in Embodiment2, a process of performing the QoS control on the uplink/downlink datapacket by the terminal is the same as a process of performing the QoScontrol on the uplink/downlink data packet by the UPF.

When needing to send an uplink data packet, the terminal performs, basedon SDF-level priorities, matching between the uplink data packet and apacket filter corresponding to an SDF with a highest priority. If thematching between the uplink data packet and the packet filtercorresponding to the SDF with the highest priority succeeds, theterminal transmits the uplink data packet by using a QoS flowcorresponding to the filter; otherwise, continues to perform matchingbetween the uplink data packet and a packet filter corresponding to anSDF with a second highest priority, until an appropriate packet filteris found through matching. When receiving the uplink data packet, theUPF performs data packet matching based on the same SDF-level QoScontrol information. Therefore, a QoS flow that is corresponding to thedata packet and that is determined by the UPF is the same as a QoS flowdetermined by the terminal, so that a packet loss can be avoided.

Embodiment 3

A specific procedure is described with reference to FIG. 8.

Step 801: A PCF sends a PDU-CAN session modification request to an SMF,where the request includes policy control rule information.

Optionally, the policy control rule information is used to establish anew policy control rule; or the policy control rule information is usedto modify an existing policy control rule; or the policy control ruleinformation is used to delete an existing policy control rule.

Step 802: After receiving the PDU session modification request, the SMFdetermines to perform a PDU session update procedure.

Step 803: The SMF sends a session management request to an AMF, wherethe session management request includes NAS signaling (for example, aPDU session modification command, where the PDU session modificationcommand is used as an example for description in the figure), and theNAS signaling includes the foregoing SDF-level QoS control information,namely, a QoS rule.

If the SMF entity determines, based on the received policy control ruleinformation, to establish a new QoS rule, the SDF-level QoS controlinformation includes a QoS rule identifier (QoS rule ID) of the newlyestablished QoS rule, a packet filter, a priority, a QFI, and a QoSparameter. For example, a format of the SDF-level QoS controlinformation may be: QoS rule ID, QFI, QoS parameters, Precedence value,Filters. If there is an existing QoS flow that can meet a QoSrequirement corresponding to the newly established QoS rule, the QFI isa QFI of the existing QoS flow. If there is no existing QoS flow thatcan meet a QoS requirement corresponding to the newly established QoSrule, a new QoS flow needs to be established, and the QFI is a QFI ofthe newly established QoS flow. Further, if the newly established QoSflow is a non-GBR QoS flow, the QoS parameter may include a 5QI. If thenewly established QoS flow is a GBR QoS flow, the QoS parameter mayinclude a 5QI, a notification, a GFBR, and an MFBR. The QoS parameter isoptional.

If the SMF entity determines, based on the received policy control ruleinformation, to modify a QoS requirement of an existing QoS rule, theSDF-level QoS control information includes an ID of the to-be-modifiedQoS rule. If an established QoS flow can meet a modified QoSrequirement, the SDF-level QoS control information includes a QFI of theestablished QoS flow. If no established QoS flow can meet a modified QoSrequirement, the SDF-level QoS control information includes a QFI of anewly established QoS flow and a QoS parameter corresponding to the newQoS flow. For example, a format of the SDF-level QoS control informationmay be: QoS rule ID, QoS flow ID, QoS parameters.

If the SMF entity determines, based on the received policy control ruleinformation, to modify a packet filter and/or a priority correspondingto an existing QoS rule, the SDF-level QoS control information includesan ID of the to-be-modified QoS rule, and a modified priority and/or amodified packet filter.

If the SMF entity determines, based on the received policy control ruleinformation, to delete an existing SDF, the SDF-level QoS controlinformation includes an ID of the to-be-deleted QoS rule.

In addition, if the SMF entity determines, based on the received policycontrol rule information, that a new QoS flow needs to be established,the session management request further independently includes QoS flowinformation, where the QoS flow information includes a QFI and a QoSparameter and is used to instruct a RAN/AN to store the QoS flowinformation and establish a corresponding air interface resource or bindthe QoS flow to an existing air interface resource. If the SMF entitydetermines, based on the received policy control rule information, thata QoS flow needs to be deleted, the session management request furtherindependently includes a QFI of the QoS flow, where the QFI is used toinstruct the RAN/AN to release an air interface resource.

Step 804: The AMF sends an N2 session request to a RAN/AN by using an N2interface, where the N2 session request includes NAS signaling (forexample, a PDU session modification command, where the PDU sessionmodification command is used as an example for description in thefigure), and the NAS signaling includes the SDF-level QoS controlinformation.

Optionally, if a new QoS flow needs to be established, the N2 sessionrequest further instructs that the RAN/AN needs to store informationabout the newly established QoS flow, and establish a corresponding airinterface resource with a terminal or bind the newly established QoSflow to an existing air interface resource. If a QoS flow needs to bedeleted, the N2 session request further instructs that the RAN/AN needsto delete corresponding QoS flow information, so that the RAN/ANreleases an air interface resource with the terminal.

Step 805: The RAN/AN sends a radio resource control request to aterminal, where the request includes a PDU session modification command,and the PDU session modification command includes the SDF-level QoScontrol information, so that the terminal performs QoS control on anuplink data packet based on the SDF-level QoS control information, ordeletes corresponding QoS rule information.

Step 806: The terminal returns an acknowledgement message to the RAN/ANafter receiving the SDF-level QoS control information.

The terminal stores the SDF-level QoS control information, and performsthe QoS control on the uplink data packet based on the SDF-level QoScontrol information, or deletes the locally stored SDF-level QoS controlinformation.

The SDF-level QoS control information may be stored in the terminal inthe following forms:

-   -   QoS Rule ID1: Precedence value, QFI, Filters;    -   QoS Rule ID2: Precedence value, QFI, Filters;    -   . . .

Step 807: The RAN/AN returns an N2 session response to the AMF by usingthe N2 interface.

Step 808: The AMF returns a session management response to the SMF,where the response includes a PDU session modification acknowledgementmessage.

Step 809: The SMF sends an N4 session modification request to the UPF byusing an N4 interface, where the request optionally includes theSDF-level QoS control information.

When the session modification request is used to add a QoS rule, the UPFgenerates, for a QoS flow corresponding to the added QoS rule based onthe SDF-level QoS control information, at least one SDF-level packetfilter of an SDF corresponding to the QoS flow, and the at least onegenerated SDF-level packet filter has a same priority.

When the session modification request is used to modify an existing QoSrule, the UPF modifies information of the QoS rule.

When the session modification request is used to delete an existing QoSrule, the UPF deletes all information of the QoS rule.

Step 810: The UPF returns an N4 session modification response to the SMFby using the N4 interface.

Step 811: The SMF returns a PDU-CAN modification acknowledgement messageto the PCF.

According to step 801 to step 811, both the terminal and the UPF performQoS control on an uplink/downlink data packet based on the sameSDF-level QoS control information.

When needing to send an uplink data packet, the terminal performs, basedon SDF-level priorities, matching between the uplink data packet and apacket filter corresponding to an SDF with a highest priority. If thematching between the uplink data packet and the packet filtercorresponding to the SDF with the highest priority succeeds, theterminal transmits the uplink data packet by using a QoS flowcorresponding to the filter; otherwise, continues to perform matchingbetween the uplink data packet and a packet filter corresponding to anSDF with a second highest priority, until an appropriate packet filteris found through matching. When receiving the uplink data packet, theUPF performs data packet matching based on the same SDF-level QoScontrol information. Therefore, a QoS flow that is corresponding to thedata packet and that is determined by the UPF is the same as a QoS flowdetermined by the terminal, so that a packet loss can be avoided.

Similarly, in some cases, alternatively, the SMF may actively initiate aprocess of modifying the SDF-level QoS control information, to bespecific, step 801 and step 811 may not be performed.

The SDF-level QoS control information in Embodiment 3 is slightlydifferent from the SDF-level QoS control information in Embodiment 1 andthe SDF-level QoS control information in Embodiment 2 in specificinformation content and an information format. However, the QoS controlinformation in Embodiment 1, the QoS control information in Embodiment2, and the QoS control information in Embodiment 3 are all implementedbased on an SDF level, and different SDFs are corresponding to differentpriorities. Therefore, in Embodiment 3, a process of performing the QoScontrol on the uplink/downlink data packet by the terminal is the sameas a process of performing the QoS control on the uplink/downlink datapacket by the UPF. Details are not described herein again.

FIG. 9 is a possible schematic structural diagram of the sessionmanagement function SMF entity in the foregoing embodiments. The SMFentity 900 can also implement a function of the SMF entity shown in FIG.5, FIG. 6, FIG. 7, or FIG. 8.

The SMF entity 900 includes a processing unit 902 and a communicationsunit 903. The processing unit 902 is configured to control and manageactions of the SMF entity. For example, the processing unit 902 isconfigured to support the SMF entity in performing the processes 501 to503 in FIG. 5, the processes 602, 603, and 609 in FIG. 6, the processes702, 703, and 709 in FIG. 7, or the processes 802, 803, and 809 in FIG.8, and/or another process used for the technologies described in thisspecification. The communications unit 903 is configured to supportcommunication between the SMF entity and another network entity, forexample, communication between the SMF entity and a functional module ora network entity shown in FIG. 5, FIG. 6, FIG. 7, or FIG. 8. The SMFentity may further include a storage unit 901, configured to storeprogram code and data of the SMF entity.

It should be noted that unit division in this embodiment of the presentapplication is an example and is merely logical function division.During actual implementation, there may be another division manner. Thefunctional units in this embodiment of the present application may beintegrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit. Theintegrated unit may be implemented in a form of hardware, or may beimplemented in a form of a software functional unit.

The processing unit 902 may be a processor or a controller, for example,may be a central processing unit (Central Processing Unit, CPU), ageneral purpose processor, a digital signal processor (Digital SignalProcessor, DSP), an application-specific integrated circuit(Application-Specific Integrated Circuit, ASIC), a field programmablegate array (Field Programmable Gate Array, FPGA) or another programmablelogic device, a transistor logic device, a hardware component, or anycombination thereof. The processing unit 902 may implement or executeexamples of various logical blocks, modules, and circuits that aredescribed with reference to the content disclosed in the presentapplication. Alternatively, the processor may be a combinationimplementing a computing function, for example, a combination includingone or more microprocessors, or a combination of a DSP and amicroprocessor. The communications unit 903 may be a transceiver. Thestorage unit 901 may be a memory.

When the processing unit 902 is a processor, the communications unit 903is a transceiver, and the storage unit 901 is a memory, the SMF entityin this embodiment of the present application may be an SMF entity shownin FIG. 10.

Based on a same technical concept, FIG. 10 is another possible schematicstructural diagram of the SMF entity in the foregoing embodiments. TheSMF entity includes a processor 1001, and a memory 1002 and atransceiver 1003 that are separately connected to the processor 1001.

The processor 1001 is configured to invoke a computer program pre-storedin the memory 1002 to perform the following steps: obtaining servicedata flow SDF-level QoS control information; and sending the SDF-levelQoS control information to a terminal by using the transceiver 1003.

In a possible implementation, the processor 1001 is further configuredto send the SDF-level QoS control information to a UPF entity by usingthe transceiver 1003, so that the UPF verifies QoS control on an uplinkdata packet based on the SDF-level QoS control information, or deletesthe SDF-level QoS control information.

In a possible implementation, when obtaining the SDF-level QoS controlinformation, the processor 1001 is specifically configured to: obtainthe SDF-level QoS control information based on a session managementrequest sent by a PCF entity; or obtain the SDF-level QoS controlinformation based on a local policy.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and at least one ofor any combination of the following: at least one packet filtercorresponding to the SDF, a priority, a QoS flow identifier, and a QoSparameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, the processor 1001 is further configuredto send, to an access network device by using the transceiver 1003, theQoS flow identifier and the QoS parameter corresponding to the QoS flow,so that the access network device establishes a corresponding airinterface resource.

FIG. 11 is a possible schematic structural diagram of the terminal inthe foregoing embodiments. The terminal 1100 can also implement afunction of the terminal shown in FIG. 6, FIG. 7, or FIG. 8.

The terminal 1100 includes a processing unit 1102 and a communicationsunit 1103. The processing unit 1102 is configured to control and manageactions of the terminal. For example, the processing unit 1102 isconfigured to support the terminal in performing the process 606 in FIG.6, the process 706 in FIG. 7, the process 806 in FIG. 8, and/or anotherprocess used for the technologies described in this specification. Thecommunications unit 1103 is configured to support communication betweenthe terminal and another network entity, for example, communicationbetween the terminal and a functional module or a network entity shownin FIG. 6, FIG. 7, or FIG. 8. The terminal may further include a storageunit 1101, configured to store program code and data of the terminal.

It should be noted that unit division in this embodiment of the presentapplication is an example and is merely logical function division.During actual implementation, there may be another division manner. Thefunctional units in this embodiment of the present application may beintegrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit. Forexample, in the foregoing embodiment, a first obtaining unit and asecond obtaining unit may be a same unit, or may be different units. Theintegrated unit may be implemented in a form of hardware, or may beimplemented in a form of a software functional unit.

The processing unit 1102 may be a processor or a controller, forexample, may be a central processing unit (Central Processing Unit,CPU), a general purpose processor, a digital signal processor (DigitalSignal Processor, DSP), an application-specific integrated circuit(Application-Specific Integrated Circuit, ASIC), a field programmablegate array (Field Programmable Gate Array, FPGA) or another programmablelogic device, a transistor logic device, a hardware component, or anycombination thereof. The processing unit 1102 may implement or executeexamples of various logical blocks, modules, and circuits that aredescribed with reference to the content disclosed in the presentapplication. Alternatively, the processor may be a combinationimplementing a computing function, for example, a combination includingone or more microprocessors, or a combination of a DSP and amicroprocessor. The communications unit 1103 may be a transceiver. Thestorage unit 1101 may be a memory.

When the processing unit 1102 is a processor, the communications unit1103 is a transceiver, and the storage unit 1101 is a memory, theterminal in this embodiment of the present application may be a terminalshown in FIG. 12.

Based on a same technical concept, FIG. 12 is another possible schematicstructural diagram of the terminal in the foregoing embodiments. Theterminal includes a processor 1201, and a memory 1202 and a transceiver1203 that are separately connected to the processor 1201.

The processor 1201 is configured to invoke a computer program pre-storedin the memory 1202 to perform the following steps: receiving, by usingthe transceiver 1203, service data flow SDF-level QoS controlinformation sent by an SMF entity; and performing SDF-level QoS controlon an uplink data packet based on the SDF-level QoS control information,or deleting the SDF-level QoS control information.

In a possible implementation, the SDF-level QoS control informationincludes: an SDF identifier; or an SDF identifier, and one of or anycombination of the following: at least one packet filter correspondingto the SDF, a priority, a QoS flow identifier, and a QoS parameter.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS flow identifier; or a QoS flow identifier, and at leastone of or any combination of the following: at least one SDF identifier,at least one packet filter corresponding to the at least one SDF, apriority corresponding to the at least one SDF, and a QoS parametercorresponding to the QoS flow.

In a possible implementation, the SDF-level QoS control informationincludes: a QoS rule identifier; or a QoS rule identifier, and at leastone of or any combination of the following: at least one packet filtercorresponding to the QoS rule, a priority, a QoS flow identifier, and aQoS parameter.

In a possible implementation, when performing the QoS control on theuplink data packet based on the SDF-level QoS control information, theprocessor 1201 is specifically configured to: determine a matching orderof SDF-level packet filters based on the priority in the SDF-level QoScontrol information; and perform data packet matching based on thematching order of the SDF-level packet filters, and perform the QoScontrol based on a QoS flow corresponding to a packet filter thatsuccessfully matches the uplink data packet.

A person skilled in the art should understand that the embodiments ofthis application may be provided as a method, a system, or a computerprogram product. Therefore, this application may use a form of hardwareonly embodiments, software only embodiments, or embodiments with acombination of software and hardware. Moreover, this application may usea form of a computer program product that is implemented on one or morecomputer-usable storage media (including but not limited to a magneticdisk storage, a CD-ROM, an optical memory, and the like) that includecomputer usable program code.

This application is described with reference to the flowcharts and/orblock diagrams of the method, the device (system), and the computerprogram product according to the embodiments of this application. Itshould be understood that computer program instructions may be used toimplement each process and/or each block in the flowcharts and/or theblock diagrams and a combination of a process and/or a block in theflowcharts and/or the block diagrams. These computer programinstructions may be provided for a general-purpose computer, a dedicatedcomputer, an embedded processor, or a processor of another programmabledata processing device to generate a machine, so that the instructionsexecuted by a computer or a processor of another programmable dataprocessing device generate an apparatus for implementing a specificfunction in one or more processes in the flowcharts and/or in one ormore blocks in the block diagrams.

These computer program instructions may be stored in a computer readablememory that can instruct the computer or another programmable dataprocessing device to work in a specific manner, so that the instructionsstored in the computer readable memory generate an artifact thatincludes an instruction apparatus. The instruction apparatus implementsa specific function in one or more processes in the flowcharts and/or inone or more blocks in the block diagrams.

These computer program instructions may be loaded onto a computer oranother programmable data processing device, so that a series ofoperations and steps are performed on the computer or anotherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or anotherprogrammable device provide steps for implementing a specific functionin one or more processes in the flowcharts and/or in one or more blocksin the block diagrams.

Obviously, a person skilled in the art can make various modificationsand variations to the embodiments of this application without departingfrom the spirit and scope of the embodiments of this application. Thisapplication is intended to cover these modifications and variationsprovided that they fall within the scope of protection defined by thefollowing claims and their equivalent technologies.

What is claimed is:
 1. A quality of service QoS control method,comprising: obtaining, by a device, service data flow SDF-level QoScontrol information for one or more SDFs from a session managementfunction entity; and performing, by the device, QoS control on an uplinkdata packet based on the SDF-level QoS control information.
 2. Themethod according to claim 1, wherein the SDF-level QoS controlinformation includes one or more QoS rules, and each SDF corresponds toa QoS rule.
 3. The method according to claim 2, wherein the one or moreQoS rules respectively comprises: a QoS rule identifier, and one of orany combination of the following: at least one SDF-level packet filter,a QoS rule precedence value, a QoS flow identifier, and a QoS parameter.4. The method according to claim 3, wherein the performing, by thedevice, QoS control on an uplink data packet based on the SDF-level QoScontrol information comprises: matching, by the device, the uplink datapacket with the at least one SDF-level packet filter in the Qos rulesbased on the QoS rule precedence values, and transmitting, by thedevice, the uplink data packet by using a QoS flow corresponding to aQoS flow identifier in a matching Qos rule whose SDF-level packet filtercan successfully matches the uplink data packet.
 5. The method accordingto claims 4, wherein the method further comprising: associating, by thedevice, the QoS flow with a DRB.
 6. A device, comprising: a memorystorage comprising instructions; and one or more processors incommunication with the memory, wherein the one or more processorsexecute the instructions to: obtain service data flow SDF-level QoScontrol information for one or more SDFs from a session managementfunction entity; and perform QoS control on an uplink data packet basedon the SDF-level QoS control information.
 7. The device according toclaim 6, wherein the SDF-level QoS control information includes one ormore QoS rules, and each SDF corresponds to a QoS rule.
 8. The deviceaccording to claim 7, wherein the one or more QoS rules respectivelycomprises: a QoS rule identifier, and one of or any combination of thefollowing: at least one SDF-level packet filter, a QoS rule precedencevalue, a QoS flow identifier, and a QoS parameter.
 9. The deviceaccording to of claim 8, wherein when performing the QoS control on theuplink data packet based on the SDF-level QoS control information, theone or more processors execute the instructions to: match the uplinkdata packet with the at least one SDF-level packet filter in the Qosrules based on the QoS rule precedence values, and transmit the uplinkdata packet by using a QoS flow corresponding to a QoS flow identifierin a matching Qos rule whose SDF-level packet filter can successfullymatches the uplink data packet.
 10. The device according to claim 9,wherein the one or more processors execute the instructions to:associate the QoS flow with a DRB.
 11. The device according to a claim6, wherein the device is a terminal.
 12. A quality of service QoScontrol method, comprising: obtaining, by a session management functionentity, service data flow SDF-level QoS control information for one ormore SDFs; providing, by the session management function entity, theSDF-level QoS control information to a terminal; obtaining, by theterminal, the SDF-level QoS control information from the sessionmanagement function entity; and performing, by the terminal, QoS controlon an uplink data packet based on the SDF-level QoS control information.13. The method according to claim 12, wherein the obtaining, by asession management function entity, SDF-level QoS control informationcomprises: obtaining, by the session management function entity, theSDF-level QoS control information based on a policy control ruleinformation or a QoS control rule from a policy control function entity;or obtaining, by the session management function entity, the SDF-levelQoS control information based on a local policy.
 14. The methodaccording to claim 13, wherein the SDF-level QoS control informationincludes one or more QoS rules, and each SDF corresponds to a QoS rule.15. The method according to claim 14, wherein the one or more QoS rulesrespectively comprises: a QoS rule identifier, and one of or anycombination of the following: at least one SDF-level packet filter, aQoS rule precedence value, a QoS flow identifier, and a QoS parameter.16. The method according to claim 15, wherein the performing, by theterminal, QoS control on an uplink data packet based on the SDF-levelQoS control information comprises: matching, by the terminal, the uplinkdata packet with the at least one SDF-level packet filter in the Qosrules based on the QoS rule precedence values, and transmitting, by theterminal, the uplink data packet by using a QoS flow corresponding to aQoS flow identifier in a matching Qos rule whose SDF-level packet filtercan successfully matches the uplink data packet.
 17. The methodaccording to claim 16, wherein the method further comprising:associating, by the terminal, the QoS flow with a DRB.
 18. A system,comprises: a session management function entity and a terminal, whereinthe session management function entity is configured to obtain servicedata flow SDF-level QoS control information for one or more SDFs, andsend the SDF-level QoS control information to the terminal, the terminalis configured to obtain service data flow SDF-level QoS controlinformation from the session management function entity, and perform QoScontrol on an uplink data packet based on the SDF-level QoS controlinformation.
 19. The system according to claim 18, wherein the SDF-levelQoS control information includes one or more QoS rules, and each SDFcorresponds to a QoS rule.
 20. The system according to claim 19, whereinthe one or more QoS rules respectively comprises: a QoS rule identifier,and one of or any combination of the following: at least one SDF-levelpacket filter, a QoS rule precedence value, a QoS flow identifier, and aQoS parameter.
 21. The system according to claim 20, wherein inperforming QoS control on an uplink data packet based on the SDF-levelQoS control information, the terminal is configured to: match the uplinkdata packet with the at least one SDF-level packet filter in the Qosrules based on the QoS rule precedence values, and transmit the uplinkdata packet by using a QoS flow corresponding to a QoS flow identifierin a matching Qos rule whose SDF-level packet filter can successfullymatches the uplink data packet.
 22. The system according to claim 21,wherein the terminal is further configured to associate the QoS flowwith a DRB.